Broadcom Advanced Control Suite Overview
Starting Broadcom Advanced Control Suite
Using Broadcom Advanced Control Suite
Broadcom Advanced Control Suite (BACS) is an integrated utility that provides useful information about each network adapter that is installed in your system. BACS also enables you to perform detailed tests, diagnostics, and analyses on each adapter, as well as to view and modify property values and view traffic statistics for each adapter.
Broadcom Advanced Server Program (BASP), which runs within Broadcom Advanced Control Suite, is used to configure teams for load balancing, fault tolerance, and virtual local area networks (VLANs). BASP functionality is available only on systems that use at least one Broadcom network adapter.
In Control Panel, click Broadcom Control Suite 4, or click the BACS icon in the taskbar located at the bottom of the Windows desktop.
Start BACS. Click the tab that provides the information of interest or from which to perform a desired test, diagnostic, analysis, or set adapter properties. To create a team, see Configuring Teaming.
The BACS interface is comprised of the following regions:
By default, the Explorer View pane is docked and pinned on the left side of the main window, the Context View pane on the right, the Context View selector below the menu bar, and the Description pane below the Context View pane. Drag the splitter between any two panes to vary the size of the panes.

You can dock and pin the Explorer View pane on the left side, right side, top, or bottom of the main window.
The Explorer View pane lists the objects that can be viewed, analyzed, tested, or configured by BACS. When an item is selected in the Explorer View pane, the tabs showing the information and options that are available for the item appear in the Context View pane.
The organization of this panel is designed to present the manageable objects in the same hierarchical manner as drivers and its subcomponents. This simplifies the management of various elements of the network interface controller (NIC). The top level of the hierarchy is the Host container, which lists all hosts managed by BACS. Below the hosts are the installed network adapters, with the manageable elements, such as physical port, VBD, and NDIS below the adapters.
The icon next to each device in the Explorer View pane shows its status. An icon next to a device name that appears normal means the device is connected and working.
The Context View selector appears below the menu bar and includes the filter and tab categories. Although you can expand and collapse the categories that appear on tabs in the Context View pane, you can alternatively display a category by selecting the box next to the category name.
In a multiple-host environment using several network adapters, there can be a large number of manageable elements per adapter that can be difficult and cumbersome to view, configure, and manage all elements. Use the filter to select a particular device function. Possible filter views include:
The Context View pane displays all the parameters that you can view for the object selected in the Explorer View pane. The parameters are grouped by tabs and categories, depending on the parameter type. The available tabs are Information, Configuration, Diagnostics, and Statistics. Because the BACS interface is context-sensitive, only the parameters that apply to the selected object can be viewed or configured in the Context View pane.
The following appear on the menu bar, but because the menu items are context-sensitive, not all items will be available at all times:
File menu
Action menu
View menu
Tools menu
Teams
The Description pane provides information, configuration instructions, and options for the selected parameter in the Context View pane.
To enable or disable the BACS tray icon
BACS places an icon in the Windows taskbar when the program is installed. Use the Options window to turn this icon on or off.
Setting the teaming mode
Setting the Explorer View refresh time
You can add one or more Windows or Linux hosts to manage from BACS.
To add a local host
To add a remote host
At the host level, you can view host information and configure parameters from the following tabs:
To view host information
Select the host in the Explorer View pane, and then select the Information tab to view host-level information.

Information Tab: Host Information
To configure the host
Select the host in the Explorer View pane, and then select the Configuration tab to configure host-level parameters.

Configuration Tab: System Management
The installed network adapters appear one level below the host in the hierarchical tree in the Explorer View pane. At the adapter level, you can view information and configure parameters from the following tabs:
The Vital Signs section of the Information tab has useful information about the network adapters that are installed in your system, such as the link status of the adapter and general network connectivity.
Select the network adapter in the Explorer View pane, and then select the Information tab to view adapter-level information.
NOTES:
The unique hardware address assigned to the network adapter.
The network address associated with the adapter. If the IP address is all 0s, the associated driver has not been bound with Internet Protocol (IP).
The status of the network link.
The adapter is operating in the indicated duplex mode.
The link speed of the adapter, in megabits per second.
The offload capabilities supported by the adapter.
The Driver Information section of the Information tab displays data about the driver for the selected network adapter.
To view Driver Information for any installed network adapter, click the name of the adapter listed in the Explorer View pane, then click the Information tab.

The status of the adapter driver.
The file name of the adapter driver.
The current version of the adapter driver.
The creation date of the adapter driver.
The Resources section of the Information tab displays information about connections and other essential functions for the selected network adapter.
To view Resources for any installed network adapter, click the name of the adapter listed in the Explorer View pane, then click the Information tab.
Note: Some information may not be available for all Broadcom network adapters.

The type of input/output (I/O) interconnect used by the adapter.
The slot number on the system board occupied by the adapter. This item is not available for PCI Express type adapters.
The bus clock signal frequency used by the adapter. This item is not available for PCI Express type adapters.
The number of bits that the bus can transfer at a single time to and from the adapter. This item is not available for PCI Express type adapters.
Indicates the number of the bus where the adapter is installed.
The number assigned to the adapter by the operating system.
The port number of the adapter. For a single-port adapter, the function number is 0. For a two-port adapter, the function number for the first port is 0, and the function number for the second port is 1.
The interrupt line number that is associated with the adapter. Valid numbers range from 2 to 25.
The memory mapped address that is assigned to the adapter. This value can never be 0.
The Hardware section of the Information tab displays information about the hardware settings for the selected network adapter.
To view Hardware for any installed network adapter, click the name of the adapter listed in the Explorer View pane, then click the Information tab.
Note: Some information may not be available for all Broadcom network adapters.

The chip version of the Broadcom adapter (this information is not available for adapters made by others).
The firmware version of the Broadcom adapter (this information is not available for adapters made by others). This information is only available for Broadcom NetXtreme adapters.
The vendor ID.
The adapter ID.
The subsystem vendor ID.
The subsystem ID.
The Network Test option on the Diagnostics tab lets you verify IP network connectivity. This test verifies if the driver is installed correctly and tests connectivity to a gateway or other specified IP address on the same subnet. The network test uses TCP/IP to send ICMP packets to remote systems, then waits for a response.
Note: The network test option is not available on adapters that are grouped into a team (see Configuring Teaming).
To run the network test
The results of the network test are displayed in the Status field.

The Diagnostic Tests option on the Diagnostics tab lets you check the state of the physical components on a Broadcom network adapter. You can trigger the tests manually, or choose to have BACS 3 continuously perform them. If the test are performed continuously, then the number of passes and fails in the Result field for each test increments every time the tests are performed. For example, if a test is performed four times and there are no fails, the value in the Result field for that test is 4/0. However, if there were 3 passes and 1 fail, the value in the Result field is 3/1.
NOTES:
To run the diagnostic tests once

This test verifies the read and write capabilities of the network adapter registers by writing various values to the registers and verifying the results. The adapter driver uses these registers to perform network functions such as sending and receiving information. A test failure indicates that the adapter may not be working properly.
This test verifies the read and write capabilities of the registers of the physical layer (PHY). The physical layer is used to control the electrical signals on the wire and to configure network speeds such as 1000 Mbit/s.
This test verifies the content of the electrically erasable programmable read-only memory (EEPROM) by reading a portion of the EEPROM and computing the checksum. The test fails if the computed checksum is different from the checksum stored in the EEPROM. An EEPROM image upgrade does not require a code change for this test.
This test verifies that the internal memory of the adapter is functioning properly. The test writes patterned values to the memory and reads back the results. The test fails if an erroneous value is read back. The adapter cannot function if its internal memory is not functioning properly.
This test verifies the operation of the internal CPUs in the adapter.
This test verifies that the Network Device Driver Interface Specification (NDIS) driver is able to receive interrupts from the adapter.
This test verifies that the NDIS driver is able to send packets to and receive packets from the adapter.
This test verifies that the NDIS driver is able to send packets to and receive packets from the adapter.
This test causes all of the port LEDs to blink 5 times for the purpose of identifying the adapter.
The Cable Analysis option on the Diagnostics tab lets you monitor the conditions of each wire pair in an Ethernet Category 5 cable connection within an Ethernet network. The analysis measures the cable quality and compares it against the IEEE 802.3ab specification for compliance.
To run a cable analysis

The valid cable distance in meters (except when the Noise result is returned).
This shows the type of link on this cable pair.
The link connection speed and duplex mode.
The status after the test is run, either completed or failed.
There are several factors that could have an effect on the test results:
Advanced on the Configurations tab allow you to view and change the values of the available properties of the selected adapter. The potentially available properties and their respective settings are described below.
NOTES:
To set adapter properties

Enables quality of service, which is an Institute of Electrical and Electronics Engineering (IEEE) specification that treats different types of network traffic diversely to ensure required levels or reliability and latency according to the type of traffic. This property is disabled by default. Unless the network infrastructure supports QoS, do not enable this property. Otherwise, problems may occur.
Enables a Gigabit Ethernet adapter to establish a link at a lower speed when only two pairs of wires are available in the cabling plant. The default setting for this property is Enabled.
Enables or disables the receipt or transmission of PAUSE frames. PAUSE frames allow the network adapter and a switch to control the transmit rate. The side that is receiving the PAUSE frame momentarily stops transmitting.
Normally, the checksum function is computed by the protocol stack. When you select one of the Checksum Offload property values (other than None), the checksum can be computed by the network adapter.
Normally, the TCP segmentation is done by the protocol stack. When you enable the Large Send Offload property, the TCP segmentation can be done by the network adapter. The default setting for this property is Enabled.
Enables the network adapter to transmit and receive oversized Ethernet frames that are greater than 1514 bytes, but less than or equal to 9000 bytes in length (9600 bytes for network adapters that operate at 10 Gbps). This property requires the presence of a switch that is able to process jumbo frames.
Frame size is set at 1500 bytes by default. To increase the size of the received frames, raise the byte quantity in 500-byte increments.
The Locally Administered Address is a user-defined MAC address that is used in place of the MAC address originally assigned to the network adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number.
The appropriate assigned ranges and exceptions for the locally administered address include the following:
Allows configuring network load balancing across multiple CPUs. The default setting for this property is Enabled.
The Speed & Duplex property sets the connection speed and mode to that of the network. Note that Full-Duplex mode allows the adapter to transmit and receive network data simultaneously.
NOTES:
Enables the network adapter to wake up from a low-power mode when it receives a network wake-up frame. Two types of wake-up frames are possible: Magic Packet and Wake Up Frame.
Sets the speed at which the network adapter connects to the network while the network adapter is in Wake on LAN mode. By default, the WOL Speed property is set to Auto.
Normally the TCP segmentation is done by the protocol stack. When you enable the Large Send Offload property, the TCP segmentation can be done by the network adapter.
Allows configuring checksum offload for the IPv4 protocol.
Allows enabling both the prioritization of network traffic and VLAN tagging. VLAN tagging only occurs when the VLAN ID setting is configured with a value other than 0 (zero).
Note: If an intermediate driver is managing the network adapter for VLAN tagging, the Priority & VLAN Disabled and Priority Enabled settings should not be used. Use the Priority & VLAN Enabled setting and change the VLAN ID to 0 (zero).
Enables VLAN tagging and configures the VLAN ID when Priority & VLAN Enabled is selected as the Priority & VLAN setting. The range for the VLAN ID is 1 to 4094 and must match the VLAN tag value on the connected switch. A value of 0 (default) in this field disables VLAN tagging.
Risk Assessment of VLAN Tagging through the NDIS Miniport Driver
Broadcom's NDIS 6.0 miniport driver provides the means to allow a system containing a Broadcom adapter to connect to a tagged VLAN. On Windows XP systems, this support was only provided through the use of an intermediate driver (e.g., Broadcom Advanced Server Program - BASP). Unlike BASP, however, the NDIS 6 driver's support for VLAN participation is only for a single VLAN ID.
Also unlike BASP, the NDIS 6.0 driver only provides VLAN tagging of the outbound packet, but does not provide filtering of incoming packets based on VLAN ID membership. This is the default behavior of all miniport drivers. While the lack of filtering packets based on VLAN membership may present a security issue, the following provides a risk assessment based on this driver limitation for an IPv4 network:
A properly configured network that has multiple VLANs should maintain separate IP segments for each VLAN. This is necessary since outbound traffic relies on the routing table to identify which adapter (virtual or physical) to pass traffic through and does not determine which adapter based on VLAN membership.
Since support for VLAN tagging on Broadcom's NDIS 6.0 driver is limited to transmit (Tx) traffic only, there is a risk of inbound traffic (Rx) from a different VLAN being passed up to the operating system. However, based on the premise of a properly configured network above, the IP segmentation and/or the switch VLAN configuration may provide additional filtration to limit the risk.
In a back-to-back connection scenario, two computers on the same IP segment may be able to communicate regardless of their VLAN configuration since no filtration of VLAN membership is occurring. However, this scenario assumes that the security may already be breached since this connection type is not typical in a VLAN environment.
If the risk above is not desirable and filtering of VLAN ID membership is required, then support through an intermediate driver would be necessary.
The information provided on the Statistics tab allows you to view traffic statistics for both Broadcom network adapters and network adapters made by others. Statistical information and coverage are more comprehensive for Broadcom adapters.
To view Statistics information for any installed network adapter, click the name of the adapter listed in the Explorer View pane, then click the Statistics tab.
Click Refresh to get the most recent values for each statistic. Click Reset to change all values to zero.
NOTES:
General Statistics show the transmitted and received statistics to and from the adapter.
A count of the frames that were successfully transmitted. This counter is incremented when the transmit status is reported as Transmit OK.
A count of the frames that were successfully received. This does not include frames received with frame-too-long, frame check sequence (FCS), length, or alignment errors, nor frames lost due to internal MAC sublayer errors. This counter is incremented when the receive status is reported as Receive OK.
A count of directed data frames that were successfully transmitted.
A count of frames that were successfully transmitted (as indicated by the status value Transmit OK) to a group destination address other than a broadcast address.
A count of frames that were successfully transmitted (as indicated by the transmit status Transmit OK) to the broadcast address. Frames transmitted to multicast addresses are not broadcast frames and are excluded.
A count of directed data frames that were successfully received.
A count of frames that were successfully received and are directed to an active nonbroadcast group address. This does not include frames received with frame-too-long, FCS, length, or alignment errors, nor frames lost because of internal MAC sublayer errors. This counter is incremented as indicated by the Receive OK status.
A count of frames that were successfully received and are directed to a broadcast group address. This count does not include frames received with frame-too-long, FCS, length, or alignment errors, nor frames lost because of internal MAC sublayer errors. This counter is incremented as indicated by the Receive OK status.
The number of frames received with CRC errors.
The total number of offloaded TCP connections.
The teaming function allows you to group any available network adapters together to function as a team. Teaming is a method of creating a virtual NIC (a group of multiple adapters that functions as a single adapter). The benefit of this approach is that it enables load balancing and failover. Teaming is done through the Broadcom Advanced Server Program (BASP) software. For a comprehensive description of the technology and implementation considerations of the teaming software, refer to the "Broadcom Gigabit Ethernet Teaming Services" section of your Broadcom network adapter user guide.
Teaming can be accomplished by either of the following methods:
NOTES:
You can create four types of load balance teams:
Smart Load Balance and Failover
In this type of team, a standby member handles the traffic if all of the load balance members fail (a failover event). All load balance members have to fail before the standby member takes over. When one or more of the load balance members is restored (fallback), the restored team member(s) resumes the handling of the traffic. The LiveLink feature is supported for this type of team.
Link Aggregation (802.3ad)
In this type of team, you can dynamically configure the network adapters that have been selected to participate in a given team. If the link partner is not correctly configured for IEEE 802.3ad link configuration, errors are detected and noted. All adapters in the team are configured to receive packets for the same MAC address. The outbound load balancing scheme is determined by the BASP driver. The link partner of the team determines the load balancing scheme for inbound packets. In this mode, at least one of the link partners must be in active mode.
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
This type of team is very similar to the link aggregation type, in that all adapters in the team must be configured to receive packets for the same MAC address. This mode does not provide link aggregation control protocol (LACP) or marker protocol support. This mode supports a variety of environments where the link partners are statically configured to support a proprietary trunking mechanism. Trunking supports load balancing and failover for both outbound and inbound traffic.
SLB (Auto-Fallback Disable)
This team is identical to Smart Load Balance and Failover, with the following exception: when the standby member is active, if a primary member comes back online, the team continues using the standby member rather than switching back to the primary member. This type of team is supported only for situations in which the network cable is disconnected and reconnected to the network adapter. It is not supported for situations in which the adapter is removed/installed through Device Manager or Hot-Plug PCI. If any primary adapter assigned to a team is disabled, the team functions as a Smart Load Balancing and Failover type of team in which auto-fallback occurs. The LiveLink feature is supported for this type of team.
You can designate one team member in an SLB type of team to be the standby member. The standby member does not actively send and receive normal network traffic while other adapters on the team are active. If all of the active adapters on the team fail or are disconnected, the standby member takes over the handling of the network activities.
In Auto-Fallback Disable mode, if a load balance member returns on line, the team continues using the standby member rather than switching back to using the load balance member. Consequently, the adapter that was initially designated a load balance member remains in an inactive state and becomes the new standby member.
LiveLink is a feature of BASP that is available for the Smart Load Balancing (SLB) and SLB (Auto-Fallback Disable) type of teaming. The purpose of LiveLink is to detect link loss beyond the switch and to route traffic only through team members that have a live link.
You can use the Broadcom Teaming Wizard to create a team, configure an existing team if a team has already been created, or create a VLAN.
To create a new team, select Create a Team from the Team menu, or right-click one of the devices in the "Unassigned Adapters" section and select Create a Team. This option is not available if there are no devices listed in the "Unassigned Adapters" sections, which means all adapters are already assigned to teams.
To configure an existing team, right-click one of the teams in the list and select Edit Team. This option is only available if a team has already been created and is listed in the Team Management pane.
Note: If you prefer to work without the wizard for now, click Expert Mode. If you want to always use Expert Mode to create a team, select Default to Expert Mode on next start. See Using Expert Mode.

Note: The team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > |


Note: There must be at least one Broadcom network adapter assigned to the team.
The TCP Offload Engine (TOE), Large Send Offload (LSO) and Checksum Offload (CO) columns indicate if the TOE, LSO, and/or the CO properties are supported for the adapter. The TOE, LSO, and CO properties are enabled for a team only when all of the members support and are configured for the feature. If this is the case, then the team offload capabilities appear on the bottom of the screen.
Note: Adding a network adapter to a team where its driver is disabled may negatively affect the offloading capabilities of the team. This may have an impact on the team's performance. Therefore, it is recommended that only driver-enabled network adapters be added as members to a team.



Note: Each LiveLink enabled team can only communicate with Probe Targets on a single VLAN. Also, VLAN ID 0 is equivalent to an untagged network. If the Probe VLAN ID is set to a value other than 0, then a VLAN must be created with an identical VLAN tag value (see Step 16.).
Note: Only the first probe target is required. You can specify up to three additional probe targets to serve as backups by assigning IP addresses to the other probe targets.
Note: All of the member IP addresses must be in the same subnet as the subnet of the probe targets.
VLANs enable you to add multiple virtual adapters that are on different subnets. The benefit of this is that your system can have one network adapter that can belong to multiple subnets.
Note: VLANs can only be created when all team members are Broadcom adapters.

Note: The team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > |



Note: You can define up to 64 VLANs per team (63 VLANs that are tagged and 1 VLAN that is not tagged). Adding several VLANS may slow down the reaction time of the Windows interface due to memory and processor time usage for each VLAN. The degree to which Windows performance may suffer depends on system configuration.


Note: At any point in the Broadcom Teaming Wizard procedure, click Preview to get a visual representation of what the team will look like before committing any changes.


Use Expert Mode to create a team, modify a team, add a VLAN, and configure LiveLink for a Smart Load Balance and Failover and SLB (Auto-Fallback Disable) team. To create a team using the wizard, see Using the Broadcom Teaming Wizard.
To set the default Teaming Mode, select Options from the Tools menu, then select Expert Mode or Wizard Mode (the default is Wizard Mode).
Note: Enabling Dynamic Host Configuration Protocol (DHCP) is not recommended for members of an SLB type of team.
Note: If you want to always use Expert Mode to create a team, click Default to Expert Mode on next start.

Note: The Create Team tab appears only if there are teamable adapters available.
Note: There must be at least one Broadcom network adapter assigned to the team.
The Large Send Offload (LSO), Checksum Offload (CO), and RSS indicate if the LSO, CO, and/or RSS properties are supported for the team. The LSO, CO, and RSS properties are enabled for a team only when all of the members support and are configured for the feature.
Note: Adding a network adapter to a team where its driver is disabled may negatively affect the offloading capabilities of the team. This may have an impact on the team's performance. Therefore, it is recommended that only driver-enabled network adapters be added as members to a team.
NOTES:
After you have created a team, you can modify the team in the following ways:
To modify a team
Note: The Edit Team tab in Expert Mode appears only if there are teams configured on the system.

You can add virtual LANs (VLANs) to a team. This enables you to add multiple virtual adapters that are on different subnets. The benefit of this is that your system can have one network adapter that can belong to multiple subnets. With a VLAN, you can couple the functionality of load balancing for the load balance members, and you can employ a failover adapter.
You can define up to 64 VLANs per team (63 VLANs that are tagged and 1 VLAN that is not tagged). VLANs can only be created when all teams members are Broadcom adapters. If you try to create a VLAN with a non-Broadcom adapter, an error message is displayed.
To configure a team with a VLAN

Note: To maintain optimum adapter performance, your system should have 64 MB of system memory for each of the eight VLANs created per adapter.
To view VLAN properties and statistics and to run VLAN tests
The procedure below applies when you are in Expert Mode.
To delete a VLAN
LiveLink is a feature of BASP that is available for the Smart Load Balancing (SLB) and SLB (Auto-Fallback Disable) type of teaming. The purpose of LiveLink is to detect link loss beyond the switch and to route traffic only through team members that have a live link.
Read the following notes before you attempt to configure LiveLink.
NOTES:
To configure LiveLink
Note: Each LiveLink enabled team can only communicate with Probe Targets on a single VLAN. Also, VLAN ID 0 is equivalent to an untagged network.
Note: Only the first probe target is required. You can specify up to 3 additional probe targets to serve as backups by assigning IP addresses to the other probe targets.
Note: All of the member IP addresses must be in the same subnet as the probe targets.
To save a configuration
The configuration file is a text file that can be viewed by any text editor. The file contains information about both the adapter and the team configuration.
To restore a configuration
Note: If necessary, go to the folder where the file is located.
Note: The team may take a very long time to restore if the team is configured with many VLANs and a static IP address.
The Statistics section shows performance information about the network adapters that are on a team.
To view BASP Statistics information for any team member adapter or the team as a whole, click the name of the adapter or team listed in the Team Management pane, then click the Statistics tab.
Click Refresh to get the most recent values for each statistic. Click Reset to change all values to zero.
This is the number of packets transmitted.
This is the number of packets discarded.
This is the number of packets queued.
This is the number of packets received.
This is the number of packets discarded.
This is the number of consecutively missed responses from a probe target before a failover is triggered.